Method and system for converting audio text files originating from audio files to searchable text and for processing the searchable text

ABSTRACT

A system and method for processing audio text files includes a content repository storing audio text files. A text transformer linguistically analyzes the audio text files within a content of multiple lexicons to form edited text results and creates a reflection repository having reflection files therein corresponding to the audio text files from the edited text results. A search engine searches the reflection files and a user device displays a first reflection file from the reflection files or a first audio text file from the audio files in response to searching.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/651,541 which is a continuation-in-part of U.S. Pat. No. 8,290,270,issued Oct. 16, 2012, which claims priority to U.S. ProvisionalApplication No. 60/851,799, filed on Oct. 13, 2006. The entiredisclosures of each of the above applications are incorporated herein byreference.

FIELD

The present disclosure relates generally to searching documents and,more specifically, to searching for information within an audio file.

BACKGROUND

The statements in this section merely provide background informationrelated to the present disclosure and may not constitute prior art.

Searching text documents using a search engine is well known. Searchingtakes place using the text within the document to identify relevantsearch results.

Often times, businesses receive a large quantity of non-text-basedmaterial. The non-text material may be referred to as image textdocuments if the image contains a number of words. Image text documentsare images of words but the words are not searchable using a searchengine. The text appears as a picture or image only and, thus, cannot besearched. The image text files may originate from various sourcesincluding faxes, forms, charts, diagrams, pictures, and the like. Oftentimes, metadata may be stored with the image to help identify the image.The metadata may contain various titles, key people, or the like. Themetadata may be manually entered for each document.

Audio files are another way in which a business may receive or storematerial. Audio files may be generated in various ways from voicemailsand audio tracks of videos. Typically, businesses have no way to searchaudio files or the content therein.

When searching image text documents, only the metadata itself issearched. The search results may have limited accuracy due to thelimited nature of the metadata. Thus, the documents found in the searchmay be limited because there is not enough identifying information inthe metadata. Consequently, desirable information may be overlooked.Therefore, it is desirable to improve the results of search engines whenfaced with image text documents.

SUMMARY

The present disclosure is particularly suitable for various types ofenterprises that have a large number of documents. The disclosure allowsimproved search results by converting audio text files to text documentsand searching using the text documents.

In one aspect of the disclosure, a method includes processing audio textfiles generated from audio files comprising linguistically analyzing theaudio text files within a context of multiple lexicons to form editedtext results, creating reflection files corresponding to the audio textfiles from the edited text results, storing the reflection files in areflection repository, processing the reflection files, and displaying afirst reflection file from the reflection files or a first audio textfile from the audio text files in response to processing.

In a further aspect of the disclosure, a system for searching audio textfiles includes a content repository storing audio text files. A texttransformer linguistically analyzes the audio text files within acontext of multiple lexicons to form edited text results and creates areflection repository having reflection files therein corresponding tothe audio text files from the edited text results. A processing toolprocesses the reflection files and a user device displays a firstreflection file from the reflection files or a first audio text filefrom the audio files in response to processing.

Further areas of applicability will become apparent from the descriptionprovided herein. It should be understood that the description andspecific examples are intended for purposes of illustration only and arenot intended to limit the scope of the present disclosure.

DRAWINGS

The drawings described herein are for illustration purposes only and arenot intended to limit the scope of the present disclosure in any way.

FIG. 1 is a block diagrammatic view of a system according to the presentdisclosure.

FIG. 2A is a flowchart illustrating a method of converting image textdocuments to text documents according to the present disclosure.

FIG. 2B is a flowchart illustrating a method of converting audio filesto text documents.

FIG. 3 is a flowchart of a method for searching and displaying accordingto the present disclosure.

FIG. 4 is a screen display of a search bar according to the presentdisclosure.

FIG. 5 is a first screen display of a search result using a first searchengine according to the present disclosure.

FIG. 6 is a second screen display of a search result using a secondsearch engine according to the present disclosure.

FIG. 7 is a screen display of a results viewer according to the presentdisclosure.

DETAILED DESCRIPTION

The following description is merely exemplary in nature and is notintended to limit the present disclosure, application, or uses. Forpurposes of clarity, the same reference numbers will be used in thedrawings to identify similar elements. As used herein, the term modulerefers to an Application Specific Integrated Circuit (ASIC), anelectronic circuit, a processor (shared, dedicated, or group) and memorythat execute one or more software or firmware programs, a combinationallogic circuit, and/or other suitable components that provide thedescribed functionality. As used herein, the phrase at least one of A,B, and C should be construed to mean a logical (A or B or C), using anon-exclusive logical OR. It should be understood that steps within amethod may be executed in different order without altering theprinciples of the present disclosure.

Referring now to FIG. 1, a document searching system 10 is illustratedhaving a content repository 12. The content repository 12 is a storagedevice that includes image text files from various sources. Image textrefers to text stored in various image formats. For example, the imagesmay be bit-mapped or formatted in other types of formats. The image textfiles may originate from various sources including faxes, forms, charts,diagrams, pictures, videos (frames) and the like. Such originations maybe associated with various formats.

An image text transformer 14 is in communication with the contentrepository 12. The image text transformer 14 includes a rover 16 forextracting and collecting images from the content repository 12. Onesuitable example of a rover is Syscom's Meta Image Rover.

The text transformer 14 may include an optical character recognition(OCR) module 18. An optional position for the OCR module 18 isillustrated outside the image text transformer 14. That is, some opticalcharacter results may be pre-generated or communicated to the image texttransformer 14. From here on, reference numeral 18 will be used to referto the OCR module regardless of position. Optical character recognitionmodule 18 forms optical character recognition results and createsreflection files in response to the results. A translation module 19 mayalso be included within the text transformer 14 or outside the texttransformer 14 as translation module 19′. The translation module 19, 19′may process the optical character recognition results and change theoptical character recognition results from a first language to a secondlanguage. This may take place before further editing or spell-checking.Of course, translation may take place after editing, spell-checking andthe like. However, the steps of editing, spell-checking,grammar-checking and the like may take place in a different language andthen translated to English, in this example.

The optical character recognition results may be edited or changed inthe editing module 20. As will be described below, the editing module 20may include various types of editing, including linguistically analyzingthe optical character recognition results, spell checking the opticalcharacter recognition results, and grammar checking the opticalcharacter recognition results. Various types of editing or no editing ofthe optical character recognition results may take place depending onthe particular system.

The optical character recognition module may perform OCR on images inthe content repository 12. Also, the OCR may be reused from anotherapplication such as facsimile recognition. One example is, whenfacsimile recognition performs OCR, only certain recognized fields areretained to form an index. The remaining OCR results are discarded. Thepresent disclosure may use the OCR results to form or add to thereflection repository 22.

The present disclosure may also be applicable to audio text files thatoriginate from audio files. An audio recognition module 21 and 21′ areillustrated within the text transformer 14 and outside of the image texttransformer 14. The audio recognition module 21, 21′ is used to convertan audio file to an audio text file. This may be performed using variouslanguages with translation to the processing language by the translationmodule 19. An audio text file originates from an audio file such as ananalog or digital audio file. Various sources such as digital recorders,tape records, videos and the like may originate audio files. The audiorecognition module 21, 21′ converts the audio file to an audio text fileusing voice recognition.

The text transformer 14 may also include an audio text rover 23. Theaudio text rover 23 may be used for extracting the audio text files fromthe content repository 12. The audio text rover 23 provides the audiotext files to the text transformer 14 from the content repository 12 forfurther processing as described below.

The text transformer 14 generates reflection files that are stored inthe reflection repository 22. The reflector files may correspond toaudio text files or image text documents. The reflection repository 22may be a separate memory storage device than the content repository 12.The reflection repository 22 may be combined with the content repository12 in terms of physical location. Also, the reflected documents may alsobe stored together with their respective document in the contentrepository. That is, a reflected document and the image text document oraudio text file may be linked. The documents and files may be linked sothat the same security for the image or audio text files is provided tothe reflected documents. The image text documents or audio text filesmay be stored in the reflection repository 22 with a unique fileextension in a form that is compatible for crawling and indexing byvarious search engines. A suitable search engine is Omnifind's®crawler/indexer or Google®.

The reflection document may be in various formats. For example, thereflection document may be in a rich text format (.rtf), a .pdf formator a .txt format. In a .txt format, the formatting may be removed. Thismay allow the reflection document to occupy less memory space.

A user device 30, having a display 32, may also be coupled to the texttransformer 14. The user device 30 may be a networked computer. The userdevice 30 may be used to modify batches and control the functioning ofthe text transformer 14.

The user device 30 may also contain a content viewer 36, a processingtool 38, and search engine 40. The content viewer 36 and the processingtool 38 may be incorporated within the user device 30 as software. Theprocessing tool may include a search engine 40, a text analytics module42 and/or a search and text analytics module 44. The search engine 40may be various types of search engines that are used to crawl, parse andindex the reflected documents stored in the reflection repository 22.The search engine 40 searches the various reflected documents andreturns search results. The text analytics module 42 may be used toanalyze the text data. For example, text analytics may compile aquantity of various types of information, including proximity to otherwords, the number of occurrences within a text and other statisticalrelationships. The text analytics module 42 may perform linguisticanalysis as well as indexing. It should be noted that text analysistypically performs a type of searching. However, the searching mentionedabove may be performed in addition to the searching of text analysis.This is set forth in the search and text analytics module 44. The searchand text analytics module 44 may provide searching in a crawl-typeenvironment as well as searching in a text analytics environment. Bothsearching and text analytics may be returned from the processing tool38.

The content viewer 36 allows the user to generate various views basedupon the search results from the processing tool 38. The content viewer36 may, for example, allow the user 32 to display the reflected documentfrom the reflection repository 22 or the image or audio text files fromthe content repository 12. Further, the content viewer 36 may allow boththe reflected document and the image text document to be viewed side byside. This will be further described in FIG. 7.

Multiple lexicons 50 may be used in the editing module 20. The lexicon50 may be derived from various sources including common words, propernames, client-specific lexicons (custom), application specific lexiconsand industry-specific lexicons.

Referring now to FIG. 2A, a method of transforming image text documentsand of forming the reflection repository 22 is set forth. In step 100,the image text files are stored in the content repository 12. The imagetext files may be compiled from various sources external to a specificcompany through the internet, or the like. Each of the image text filesmay also have metadata associated therewith.

In step 102, the various batches are managed. Batches define a logicalunit of work or set of documents upon which the system services willoperate. The system will operate on the set of documents in a batchsequentially. Managing the batches also includes coordinating threads totake advantage of processing schedules using multiple CPUs and managememory. The system may operate upon multiple batches in parallel. Thesystem also allows administrators to coordinate system execution timeframes and batch sizes. Managing batches 102 may also include stagingthe batches including kicking off the batch of work to the stagingphase.

In step 104, the batches may be staged. If the device is on a tapedevice or in off-line storage, the documents may be pre-fetched. Bypre-fetching documents, tape-stored documents or off-line storage avoidsa subsequent delay time during the processing. Staging may alsodetermine whether or not the document is within a database table. Thatis, the documents may be within a database instead of being within afile system. If the files are within a database, segments may be built.The rows of data in the database (BLOBs) may be used to create a file ifthis document is within a database. The staging phase 104 may also trackthe results of the staging phase, including the quantity of documents,time to execute, size of documents, and the number of errors.

In step 106, roving of the content repository using the text transformermay be managed. Roving is used to translate an image to text. Variousparameters may be set for performing the roving. Managing the roving maycoordinate threads to take advantage of processing schedules, use ofmultiple CPUs, and manage memory. The system may operate upon multiplebatches in parallel. The system may allow administrators to define thelevel of parallel roving to manage. Managing the roving may also includesplitting the work up into multiple streams to be operated upon.

In box 108, several steps that illustrate roving are set forth. Theroving may take place using the image rover 16. In step 110, the imagefiles are retrieved by the image text transformer 14 from the contentrepository 12. The metadata may also be retrieved in step 112. In step114, the recognition of a particular form may be performed. For example,if the document is a particular type of document, this type of form maybe recognized in the form-recognition step of 114. In step 116, if thedocument includes bar codes or supports bar-code recognition, a bar codetransformation process may take place. The bar codes may, thus, beinterpreted also in step 116. In step 118, an optical characterrecognition (OCR) process may be performed on the documents. The OCRprocess may use a number of types of processing.

As mentioned above, the OCR may be performed as a result of anotherprocess such as a facsimile recognition process that typically discardsOCR results after field indexing is performed.

Step 120 performs editing steps. In step 120, the OCR results may betranslated from a first language to a second language. In step 121,lexicons may be formed. The lexicons may be derived from extractions ofa customer's structure data or may be a third-party linguisticanalytical engine. Common lexicons may also be used as well as standardproper lexicons. Thus, various lexicons may be used to improve theoptical character recognition results and/or the translated results. Ofcourse, translation may occur after text resolution. In step 122, thelexicons are used to perform text resolution from the results of theoptical character recognition. The text resolution is part of an editingblock 126.

In step 123, linguistic analysis from a third-party analytic engine mayalso be used to help resolve the results of the optical characterrecognition. Further editing may include a grammar check 124. Varioustypes of grammar checking are known, such as those used in wordprocessors. In step 126, further editing may also take place. The spellcheck may be similar to that set forth in a word processor. It should benoted that the editing in steps 122-125 may be split apart and processedin parallel batches. An edit manager may be used to schedule and performthe edits illustrated in steps 122-125. After the editing steps in box126, the text transformer in step 128 may encode the edited image textdocuments for storage in the reflection repository 22 as reflectiondocuments. In step 130, the reflection documents are stored in thereflection repository. A reflection repository may also store metadata.

The linguistic analysis, grammar check and spell check may be used tochange the reflected document or may also be used to change themetadata. That is, if a grammar error in linguistic or spelling check isnoted, the reflection document itself may not be modified but themetadata may be modified instead. Another alternative is for the end ofthe document to be modified with the correct grammar, spelling check, orlinguistic change within the document but at the end of the document atthe point of the change within the document.

The encoding and storing may be formed so that the reflected documentsmay easily be searched. The storing, as mentioned above, may also takeplace in the content repository. The reflected documents may be linkedtogether with the image text document. Linking may be performed so thatthe same security for the image text document is applied to thereflected document. Each of the documents may have different levels ofsecurity, depending on the information contained therein.

Referring now to FIG. 2B, a method of forming documents in a reflectionrepository from audio files is set forth. In step 132, audio files areobtained and stored within the content repository 12. As mentionedabove, various sources may provide audio files including from theInternet or various sources within a company such as a voicemail system,dictation systems, or the like. In step 134, the audio files may beprocessed in batches. Step 134 manages the batches for processing.Managing batches is described above relative to step 102 in FIG. 2A. Instep 136, the batches may be staged. Staging the batches is describedabove relative to step 104 and thus will not be repeated.

In step 138, roving of the content repository using the text transformermay be managed. Roving involves retrieving the audio files andperforming audio recognition thereon. The management of roving mayinclude splitting the work into multiple streams to be operated upon bythe text transformer.

Box 140 illustrates the steps to be performed in the roving process.Step 142 retrieves the audio file from the content repository. Step 144retrieves any metadata associated with the audio files. This may includethe author or speaker in the audio file, the time of the audio file, andother indications of origin of the audio file. The metadata may alsoinclude the subject and key words associated with the audio file. Instep 146, audio recognition of the audio file is performed. Audiorecognition may, for example, be voice recognition. As is illustrated inFIG. 1, the audio recognition may take place outside of the texttransformer inside the text transformer using the audio recognitionmodules 21, 21′. The result of step 146 is audio text files.

After the initial audio recognition, the audio text files may be editedand translated in step 148. As mentioned above, translation may takeplace after grammar and spell-checking. A series of steps performedduring editing in step 150 is set forth. As described above, lexiconsmay be formed and used in the processing. Lexicons may be derived fromextractions of customer's structured data or may be a third-partylinguistic and analytical tool. Within the context of multiple lexicons,the text document may be improved in step 154. In step 156, linguisticanalysis may also be performed.

In step 156, linguistic analysis may also be performed on the audio textfile to form edited results. For example, a third-party analyticalengine may be used as described above in step 132 to form further editedresults. Further, steps 158 for grammar-checking and 160 forspell-checking correspond to steps 134 and 136, respectively. Asmentioned above, various types of grammar and spell-checking similar tothat set forth in a typical word processor may be used.

In steps 162 and 164, the edited results may be encoded and stored inthe reflection repository. These steps are similar to the steps setforth above relative to the image text files. Step 162 encodes theedited results for storage within the reflection repository to form thereflection documents. Step 164 stores the reflection documents in thereflection repository. Metadata may also be stored with the reflectiondocuments. The reflection documents correspond to the audio text files.

Referring now to FIG. 3, a method for using the reflected documents isset forth. In step 180, a search engine may crawl the reflectedrepository. That is, the reflection repository documents may betraversed. In step 182, the reflected repository documents may be parsedso that the text of the documents is examined. In step 184, an index ofthe reflection repository may be created. The index creates a searchabletext repository. The steps 180-184 may be performed at various times,including during an initial search, prior to any searching or after newdocuments are added to the reflection repository.

In step 186, the user initiates the processing tool of FIG. 1. In step188, the user formulates search words or search strings of interest tothe user. Text analysis criteria may also be set by the user. Certainterms or relative placement may be adjusted. In step 190, a searchand/or text analytics of the reflected documents is performed. A searchor text analytics of the metadata may also be performed simultaneouslywith a search of the reflected documents in step 192. Searching and textanalytics take place using the processing tool 38 illustrated in FIG. 1.In step 194, search and text analytics results may be viewed with theuser device. Examples of screen displays of search results are set forthin FIGS. 4 and 5.

In step 196, the reflected documents may be viewed. In step 198, theoriginal image text document may also be viewed. It should be noted thatthe reflected document may be viewed together with the original documentas illustrated in FIG. 7. However, either of the reflected document orthe original image, audio text file or original audio file may also beviewed or listened to. As mentioned above, in certain situations thereflected documents may be discarded or deleted after the search indexis formed. Therefore, only the image, audio text file or original audiofile may be viewed or listened to, but the reflected documents used toperform the search index and finding the image or audio text file arenot viewed.

In step 200, the documents may be manipulated. That is, various portionsof the document may be scrolled, zoomed, panned, rotated, fitted, sized,or negatives made. Also, further manipulations may be performed byannotating, copying, sending, printing, or changing the properties ofthe document. Spell checking and grammar checking may also be performedafter viewing the reflected document. The changes may be performed inthe reflected document or in the metadata. Other manipulations includesynchronizing the document, highlighting, dual highlighting, scrolling,dual scrolling, viewing edits, and the like. The viewing edits may beperformed by looking at both documents and editing the text of thereflected document.

Referring now to FIG. 4, a search bar 300 is illustrated having varioussearch selections 302. In this example, the search engine used may beOmnifind® or Google®. Either of these may be selected for the searchengine. In box 304, the user may input various search terms. Box 306allows the user to get the original document.

Referring now to FIG. 5, a window 400 in a browser illustrating thesearch results 402 is illustrated. In this example, the relevancy numberis indicated at 404. Also, the date the document was created isillustrated at 406. The document title is illustrated at 408. It shouldbe noted that the document title may be formed from the image textdocument or may be formed from metadata associated with the image textdocument or a combination of both. Under the title, portions of thereflected document 410 may be provided with the search term highlightedtherein. Each of the results may contain similar formatting with adifferent relevancy depending on the frequency of the search termselected by the user. The search results are from an Omnifind® searchengine.

Referring now to FIG. 6, a window 450 illustrating the results of asearch using Google® is illustrated. In this example, the titles of thedocument are illustrated at 452. Also, portions of the document are setforth in 454. The display is set up in terms of relevancy.

Referring now to FIG. 7, a screen display 500 is illustrated having afirst image text document 502 from the image text documents displayedside-by-side with a first reflected document 504 from the reflecteddocuments. As can be seen, a direct correspondence is set forth betweenthe terms in the image text document 502 and the reflected document 504.During this time, the user may choose to manipulate, add to, orotherwise change the reflected document or its metadata.

Those skilled in the art can now appreciate from the foregoingdescription that the broad teachings of the disclosure can beimplemented in a variety of forms. Therefore, while this disclosureincludes particular examples, the true scope of the disclosure shouldnot be so limited since other modifications will become apparent to theskilled practitioner upon a study of the drawings, the specification andthe following claims.

What is claimed is:
 1. A method of processing audio text files generatedfrom audio files comprising: receiving audio text files at or fromwithin electronic text transformer; translating the audio text filesfrom a first language to a second language; after receiving thetranslated audio text files, in an editing module of the electronic texttransformer, linguistically analyzing the audio text files within acontext of multiple lexicons to form edited text results, said multiplelexicons comprising more than one of common words, proper names, clientspecific lexicons, application specific lexicons, industry specificlexicons and third party lexicons; electronically creating reflectionfiles corresponding to the audio text files from the edited textresults; electronically communicating the reflection files to anelectronic reflection repository; storing the reflection files in theelectronic reflection repository; processing the reflection files byforming a search index from the reflection files and searching, inresponse to a user request, the search index, or text analyzing thereflection file using the search index; searching metadata associatedwith the reflection files or text analyzing metadata associated with thereflection files; and at a display of a user device, displaying a firstreflection file from the reflection files or a first audio text filefrom the audio text files in response to processing and, searchingmetadata associated with the reflection files or text analyzing themetadata associated with the reflection files.
 2. A method as recited inclaim 1 further comprising at least one of storing the audio text filesin a content repository prior to linguistically analyzing and storingmetadata associated with the audio text files in the reflectionrepository.
 3. A method as recited in claim 1 wherein the multiplelexicons include custom lexicons.
 4. A method as recited in claim 1further comprising at least one of grammatically analyzing the editedtext results and spell checking the edited text results.
 5. A method asrecited in claim 1 further comprising displaying at least one of aplurality of search results, a first reflection file from the reflectionfiles and an audio text file in response to searching.
 6. A method asrecited in claim 1 further comprising displaying a first reflection filefrom the reflection files and a first audio text file.
 7. A method asrecited in claim 1 wherein the reflection repository and a contentrepository storing the audio text files are co-located.
 8. A method asrecited in claim 1 further comprising linking a first audio text fileand a first reflection file from the reflection files in a contentrepository.
 9. A method as recited in claim 1 further comprising linkinga first audio text file and a first reflection file from the reflectionfiles in a content repository with a security setting of the first audiotext file.
 10. A method as recited in claim 1 further comprising atleast one of forming a search index from the reflection files andsearching the search index, and forming the search index from thereflected files, searching the search index and deleting the audio textfiles after forming the search index.
 11. A method as recited in claim 1further comprising associating respective metadata with each of theaudio text files.
 12. A method as recited in claim 11 further comprisingat least one of naming each audio text file in response to therespective metadata, and naming each audio text file of the audio textfiles in response to the respective metadata and wherein searchingcomprises searching content of each audio text file of the audio textfiles and the respective metadata.
 13. A system for processing audiotext files generated from audio files comprising: an electronic texttransformer associated with a processor linguistically analyzing theaudio text files within a context of multiple lexicons to form editedtext results, said multiple lexicons comprising more than one of commonwords, proper names, client specific lexicons, application specificlexicons, industry specific lexicons and third party lexicons, saidtransformer creating electronic reflection files corresponding to theaudio text files from the edited text results; an electronic reflectionrepository in communication with the text transformer storing theelectronic reflection files therein; a processing tool processing, inresponse to a user request, the reflection files by forming a searchindex from the reflection files and searching the search index, or textanalyzing the reflection files using the search index and saidprocessing tool searching metadata associated with the reflection filesor text analyzing metadata associated with the reflection files; and auser device displaying on a display a first reflection file from thereflection files or a first audio text file from the audio text files inresponse to processing and, searching, in response to a user request,metadata associated with the reflection files or text analyzing themetadata associated with the reflection files, said user devicedisplaying a search bar for inputting search terms into the processingtool.
 14. A system as recited in claim 13 further comprising a contentrepository storing the audio text files therein.
 15. A system as recitedin claim 14 wherein the content repository stores reflection files ormetadata associated with the audio text files therein, or bothcomprising at least one of wherein the reflection repository and thecontent repository are co-located and wherein the text transformerstores the reflection files in the content repository and wherein thecontent repository stores metadata associated with the audio text files.16. A system as recited in claim 13 wherein the text transformergrammatically analyzes the audio text files to form the edited textresults or spell checks the audio text files to form the edited textresults or both.
 17. A system as recited in claim 13 wherein the userdevice displays a plurality of search results in response to searching.18. A system as recited in claim 17 wherein the user device selects afirst search result from the plurality of search results and displays afirst reflection file from the reflection files or a first audio textfile from the audio text files.
 19. A system as recited in claim 17wherein the user device displays a first reflection file from thereflection files and a first audio file.
 20. A system as recited inclaim 13 wherein the text transformer links a first audio text file anda first reflection file from the reflection files in a contentrepository.
 21. A system as recited in claim 13 wherein the texttransformer links a first audio text file and a first reflection filefrom the reflection files in a content repository with a securitysetting of the first audio text file.
 22. A system for processing audiotext files generated from audio files comprising: a translation moduletranslating the audio text files and communicating the audio text filesto an electronic text transformer; the electronic text transformerassociated with a processor linguistically analyzing the translatedaudio text files within a context of multiple lexicons to form editedtext results, said multiple lexicons comprising more than one of commonwords, proper names, client specific lexicons, application specificlexicons, industry specific lexicons and third party lexicons, saidtransformer creating electronic reflection files corresponding to theaudio text files from the edited text results; an electronic reflectionrepository in communication with the text transformer storing theelectronic reflection files therein; a processing tool processing thereflection files by forming a search index from the reflection files andsearching the search index, or text analyzing the reflection files usingthe search index, and said processing tool searching metadata associatedwith the reflection files or text analyzing metadata associated with thereflection files; and a user device displaying on a display a firstreflection file from the reflection files or a first audio text filefrom the audio text files in response to processing, and searching, inresponse to a user request, metadata associated with the reflectionfiles or text analyzing the metadata associated with the reflectionfiles, said user device displaying a search bar for inputting searchterms into the processing tool.